═══ 1. FontFolder Overview ═══ FontFolder provides an easy, efficient way to manage Adobe Type 1 fonts (also known as ATM fonts) in OS/2. Once a font is registered with the FontFolder Master Library, the font can be loaded and unloaded in OS/2 from the FontFolder main window with simple point and click operations. With FontFolder you only need to keep loaded those fonts that you are currently using. This saves time and resources since OS/2 only needs to load a small number of fonts on bootup and keep a small number of fonts in memory at any one time. Applications that load all the installed fonts when starting will also start faster. See the following for additional information. Topics: o Overview of ATM Fonts o Overview of OS/2 Fonts o Installing FontFolder o Using FontFolder o Removing FontFolder o Creating and Maintaining the Master Library o Installing Fonts in OS/2 o Removing fonts from OS/2 o FontFolder Menus o Error Recovery ═══ 2. Overview of ATM Fonts ═══ ATM font is the popular name for an Adobe Type 1 font, originated by Adobe Systems Incorporated. These fonts are scalable, meaning the system can accurately generate font characters in a wide range of sizes from one font description. This is in contrast to bit-mapped fonts, where there must be a complete, separate font description for each size. ATM fonts can be used for both display and printing and are supported on numerous operating systems in addition to OS/2. As a result thousands of fonts are available from a wide variety of sources. There are also programs available that allow you to generate your own ATM font design. An ATM font comes from the supplier as a collection of files. There is always a file with a name of the form filename.PFB which contains the detailed information needed to construct the font characters. There will be one or more additional files for each font as well. Fonts shipped by Adobe contain a filename.AFM file and a filename.INF file in addtion to the filename.PFB file. For use in OS/2, the PFB file and the AFM file are required. Microsoft Windows (and hence WinOS2) requires the PFB file and a file called filename.PFM. The ATM Control Panel used to install ATM fonts in Windows can use the AFM file and the INF file to construct a PFM file. Some font vendors aiming solely at the Windows market have unfortunately taken to shipping ATM fonts with only the PFB and PFM files. Such fonts are not immediately usable in OS/2. The first recourse is to contact the vendor to attempt to obtain the corresponding AFM file. Vendors such as Adobe are usually quite willing to supply these for free, in fact Adobe has provided a large number of AFM files for their type library in the ADOBE and DTPFORUM forum libraries on Compuserve. There are also font editing programs that will produce an AFM file from the PFB and PFM file and some utilities that attempt to convert a PFM file to an AFM file. ═══ 3. Overview of OS/2 Fonts ═══ OS/2 uses both bit-mapped fonts and ATM fonts for displaying characters. FontFolder does not deal with the OS/2 bit-mapped fonts. OS/2 ships with a basic set of ATM fonts whose files can be found in the \PSFONTS directory on the OS/2 boot drive. An ATM font for OS/2 must have both a filename.AFM and a filename.PFB file. In order for OS/2 to recognize these files they most both reside in the same directory. However, different fonts can reside in different directories. OS/2 keeps a record in the OS2.INI file of the path to each installed font. Note: Once consequence of this is that the user must not move the files for an installed font to a different location without first uninstalling the font from OS/2. Once the files are moved, the font can be reinstalled in OS/2. OS/2 requires that the font files for an installed font reside on a hard drive. One reason for this is that OS/2 reads these files on bootup to generate the required information on installed fonts. As a result, when a font is installed in OS/2 from a removable drive such as a floppy drive or CDROM drive the font files must be copied to a directory on a hard drive. The OS/2 Font Pallete defaults to \PSFONTS as the location for these files, but the user can change this to any directory. FontFolder also copies these files to a user-designated hard drive location when registering a font with the Master Library from a removable drive. After this, FontFolder never moves the files again when installing and uninstalling the font in OS/2. When an ATM font is installed in OS/2, a compressed equivalent of the AFM file named filename.OFM is generated and placed in the same directory as the PFB file. The OS/2 Font Pallete does not use the AFM file except for installation, and does not copy the AFM file to the target directory. FontFolder copies both the AFM file and the PFB file to the target directory when registering the font with the Master Library from a removable drive. The first time the font is installed in OS/2 FontFolder puts the OFM file created in the existing directory with the AFM and PFB file for the font. FontFolder does not at this time offer the option of automatically erasing the AFM file at this point, however the user is free to erase the AFM file once the OFM file has been created (FontFolder shows the OFM file has been created by changing the font filename entry in the Master Library from AFM to OFM). ═══ 3.1. Windows Fonts in OS/2 ═══ OS/2 uses and manage ATM fonts in WinOS2 in the same way as Windows. This means that OS/2 requires either a filename.PFM file or a filename.INF file in addition to the filename.PFB file to install the font in WinOS2. When the font is installed in WinOS2 via the ATM Control Panel (FontFolder does not manage ATM fonts for Windows), ATM will move the PFM file to a subdirectory named PFM under the directory containing the PFB file, creating the subdirectory if necessary. OS/2 and WinOS2 can share the same PFB file using a directory structure as shown below │ ┌─────────┐ ├──┬─┤MYFONTDIR│ │ │ └─────────┘ │ ├─ filename.afm (ofm) │ │ ├─ filename.pfb │ │ ┌─────────┐ └─┬─┤ PFM │ │ └─────────┘ │ └─ filename.pfm When FontFolder registers a font with the Master Library from a removable drive, it will also copy either the WinOS2 filename.PFM file to a PFM subdirectory, creating the directory if necessary, or if it finds a filename.INF file but no PFM file, the filename.INF file to the directory containing the AFM and PFB files, provided the user has checked the Copy Windows Font Files box. ═══ 4. Installing FontFolder ═══ This section provides a description of what files and system file entries are created when FontFolder is installed and first opened, and the system resources used by FontFolder. To continue in this section choose one of the following: o FontFolder Files o FontFolder Memory Requirements o Other FontFolder Resource Requirements ═══ 4.1. FontFolder Files ═══ The only files required to use FontFolder are FONTFOLD.EXE and FONTFOLD.HLP. FONTFOLD.EXE can be installed anywhere on the system. FONTFOLD.HLP can be installed either in the same directory as FONTFOLD.EXE or in any directory specified in the set HELP= line in the OS/2 CONFIG.SYS file. It is recommended that FONTFOLD.HLP be kept in the same directory as FONTFOLD.EXE. The first time FontFolder starts it asks the user to provide paths to use to store two files that FontFolder generates during operation. The default in both cases is to store them in the same directory as FONTFOLD.EXE. The first of these files, FONTFOLD.INI, keeps key information about the user preferences for FontFolder such as size and screen position of the main window, etc., and is created the first time FontFolder is closed. One case where one might place this file in a separate directory is if FontFolder is being shared on a network. If the user chooses to place FONTFOLD.INI in a location other than the default, then FontFolder writes this location to OS2.INI. If FONTFOLD.INI is left in the default directory then no entry is made in OS2.INI. The second file that FontFolder creates as part of its operation is called MASTLIB.FF1, and contains information identifying all the fonts registered with the FontFolder Master Library. FontFolder creates this file the first time it is closed or when the user chooses Save Master Library from the Master Library menu. The location of this file is kept in FONTFOLD.INI. FontFolder will also maintain one generation of backup of MASTLIB.FF1 called MASTLIB.BAK in the same directory as MASTLIB.FF1. The combined size of these files should be no more than about 200KB in the worst case. ═══ 4.2. FontFolder Memory Requirements ═══ When in use FontFolder keeps the Master Library and OS/2 Installed Fonts information in linked lists that require about 560 bytes of memory per font entry. Sufficient memory is allocated to allow storing over 1200 fonts in the Master Library, while the number of fonts actually installed in OS/2 should normally be less than 100 (for performance reasons). Thus maximum use would require somewhat less than one megabyte of memory beyond what the program normally takes. This limit is unlikely to be reached in practice because of the OS/2 limit on listbox contents. Since FontFolder uses OS/2's sparse memory allocation methodology, only enough memory is committed to hold the actual font information. ═══ 4.3. Other FontFolder Resource Requirements ═══ FontFolder uses the standard OS/2 listboxes to display the Master Library and Installed Fonts lists. In OS/2 2.1 the total contents of all listboxes in the system is limited to 64 KB. In the worst case of displaying the fully qualified path name view of these lists each entry can be up to 260 bytes, so the total number of fonts that could be displayed in this worst case condition would be around 250 fonts if no other open applications are using listboxes. However, this only applies if the user has specified very long directory paths for the font files. In a more typical case of perhaps 50 characters per path name, FontFolder would be able to display over 1300 fonts. If you have a large number of fonts and run in to this limit, see the Listbox error help for directions on how to recover. ═══ 5. Using FontFolder ═══ FontFolder works on the principle of keeping two separate lists of ATM fonts which are displayed at all times in the main FontFolder window. 1. The OS/2 Installed Fonts list The Installed Fonts list is simply the list of fonts that are actually installed in OS/2 and available for use. It is the same list one sees from the OS/2 Font Pallete or from the Font Dialog of an OS/2 application. 2. The Master Library list The Master Library list of fonts is a larger list of all fonts that FontFolder knows about, whether they are currently installed in OS/2 or not. In normal operation this list will be larger than the number of Installed Fonts, in some cases substantially so. The user creates this list by registering fonts with the Master Library using FontFolder's editing capability available from the Master Library pulldown on the menu bar. The only limit to registering fonts with the Master Library other than resource limits (see Installing FontFolder ) is that in Version 1.0 this list may only contain font files that reside on a nonremovable hard drive. Note: The user may still register fonts residing on removable media with the Master Library. FontFolder will copy the necessary files to a user-designated directory on a hard drive as part of the registration process. For further information on using FontFolder see the following: o Starting FontFolder for the first time o Everyday FontFolder use ═══ 5.1. Starting FontFolder for the first time ═══ Once FontFolder has been installed by copying FONTFOLD.EXE and FONTFOLD.HLP to the system, FontFolder is ready for use. The first time FontFolder is started it will display the FontFolder Setup Dialog which asks for three pieces of information: o The Drive letters of all the removable drives on the system o The location to store the initialization file FONTFOLD.INI o The location to store the Master Library data file MASTLIB.FF1 See the FontFolder Setup Dialog Help for details on the meaning and values for these settings. The first thing FontFolder does on startup is to read in the list of fonts already installed in OS/2 from OS2.INI. It is possible for this list to include corrupted font files. If FontFolder encounters a file that it can not successfully read to obtain the required font information, it displays a dialog box giving the details of the suspect font and offering the user the option to remove it from OS2.INI. The user should normally take this option since FontFolder can not deal with this file (and OS/2 can not use it) and will redisplay this error message on every startup until the font is removed. In any case FontFolder will not list the font in the Installed Fonts list. See the Load Installed Fonts List Dialog Help for details. On the first startup FontFolder generates an initial Master Library by copying the list of fonts already installed in OS/2 to the Master Library list. From this point on the user is free to add or delete entries in the Master Library independent of what fonts are actually installed in OS/2. ═══ 5.2. Everyday FontFolder use ═══ Once a font is registered with the Master Library the user can install the font in OS/2 by selecting the font from the Master Library list and clicking on the Install button. Multiple selections are permitted. To remove (uninstall) a font from OS/2 the user selects the font in the Installed Fonts list and clicks on the Remove button. Installing and removing fonts in this manner has no effect on the Master Library list. Separate editing facilities are provided for maintaining the Master Library. When a font is registered with the Master Library, FontFolder creates an entry which contains both the name of the font (e.g. Courier Bold) and the fully qualified path to the font files. If the source for the files is a removable medium such as a diskette or a CDROM, FontFolder copies the files to a user-designated directory on a hard drive at the time of registration. It is this hard drive location that is stored in the Master Library. When a font is installed in OS/2 from the Master Library, no files are moved. FontFolder simply provides OS/2 with the information on where to find the font files. Similarly, when a font is removed from OS/2, no files are moved. Only the entries in OS/2 referring to these files are deleted. This means that the user has complete freedom in organizing font files in whatever directory organizations make sense. The user has the option of Saving the Master Library at any point. If the Master Library has been changed but not saved when FontFolder is closed, the user is prompted as to whether the Master Library changes should be saved or discarded. FontFolder keeps one level of backup of the Master Library file, and there is provision for the user to Revert to the backup copy of the Master Library. The Installed Fonts information is always saved as soon as a font is installed or removed from OS/2. For details on using FontFolder see o Registering Fonts with the Master Library o Deleting Fonts from the Master Library o Saving the Master Library o Reverting the Master Library o Installing Fonts in OS/2 o Removing Fonts from OS/2 o Views of Fonts o FontFolder Settings ═══ 6. Removing FontFolder ═══ FontFolder can be removed from the system by finding and deleting the following files o FONTFOLD.EXE o FONTFOLD.HLP o FONTFOLD.INI o MASTLIB.FF1 o MASTLIB.BAK If the user has never changed the default settings, all of these files should be in the same directory. If the user specified other paths for the FONTFOLD.INI file or for the MASTLIB.* files, these paths must be searched as well. If the FontFolder Settings for these paths were changed multiple times while FontFolder was installed, there could be copies of these files in each of these paths. If a path other than the default was specified for FONTFOLD.INI, this information was recorded in OS2.INI under the application name FontFolder. This entry can be removed from OS2.INI by resetting the FONTFOLD.INI path to the same directory as FONTFOLD.EXE using Settings. There are no other changes that FontFolder makes to the system. ═══ 7. Creating and Maintaining the Master Library ═══ FontFolder is built around the concept of a Master Library in which the user registers all the fonts that are available for installation in OS/2. Once a font is registered with the Master Library, the user can install it in OS/2 with simple point and click operations from the FontFolder main window. When a font is registered with the Master Library, FontFolder creates an entry which contains both the name of the font (e.g. Courier Bold) and the fully qualified path to the font files. If the source for the files is a removable medium such as a diskette or a CDROM, FontFolder copies the files to a user-designated directory on a hard drive at the time of registration. It is this hard drive location that is stored in the Master Library. When a font is installed in OS/2 from the Master Library, no files are moved. FontFolder simply provides OS/2 with the information on where to find the font files. Similarly, when a font is removed from OS/2, no files are moved. Only the entries in OS/2 referring to these files are deleted. This means that the user has complete freedom in organizing font files in whatever directory organizations make sense. Deleting a font from OS/2 has no effect on the Master Library entry. For additonal details see the following: o Creating the Master Library o Maintaining the Master Library ═══ 7.1. Creating the Master Library ═══ On the first startup FontFolder generates an initial Master Library by copying the list of fonts already installed in OS/2 to the Master Library list. From this point on the user is free to add or delete entries in the Master Library independent of what fonts are actually installed in OS/2. ═══ 7.2. Maintaining the Master Library ═══ Maintenance of the Master Library is done by selecting Master Library from the main window menu bar. From this pulldown the user can choose to o Register fonts o Delete fonts o Save the Master Library to disk o Revert to a previous version of the Master Library o View a Font Information popup that displays the information stored in the Master Library for any Master Library font. The user has the option of Saving the Master Library at any point. If the Master Library has been changed but not saved when FontFolder is closed, the user is prompted as to whether the Master Library changes should be saved or discarded. FontFolder keeps one level of backup of the Master Library file, and there is provision for the user to revert to the backup copy of the Master Library. ═══ 8. Installing Fonts in OS/2 ═══ In order to install a font in OS/2 the font must first be registered with the Master Library. To install one or more fonts in OS/2, first mark the fonts to be installed in the Master Library list. Then click on the Install button. Multiple fonts are marked/unmarked by holding down the Ctrl key while marking. A consecutive set of fonts in the list can be marked by holding down the Ctrl key and dragging the mouse in the list. Once a font is installed in OS/2 from FontFolder it is immediately available for use by applications. Some applications may need to be restarted in order to see the newly installed fonts. A few applications manage their own font lists. These applications may or may not see all fonts installed in OS/2. If a newly installed font does not show up in your application, try opening the OS/2 Font Pallete and looking in the list of fonts shown via the Edit font button. If the font shows up in the Font Pallete list it is properly installed in OS/2. In this case you should contact your application vendor to find out how they are managing fonts. ═══ 9. Removing Fonts from OS/2 ═══ To remove one or more fonts from OS/2, first mark the fonts to be removed in the OS/2 Installed Fonts list. Then click on the Remove button. Multiple fonts are marked/unmarked by holding down the Ctrl key while marking. A consecutive set of fonts in the list can be marked by holding down the Ctrl key and dragging the mouse in the list. Removing fonts from OS/2 is a complicated operation. It is best understood by thinking of OS/2 keeping two lists of fonts. o The first OS/2 list is the long term list, kept in OS2.INI, which tells OS/2 which fonts to load on bootup. FontFolder always updates this list when a font is removed from OS/2, so the font will be gone on the next OS/2 bootup. o The other OS/2 font list is the list of fonts currently loaded and available in memory. Since multiple applications can be running in OS/2 simultaneously, OS/2 must protect one application from another application unloading a font that the first application is currently using. OS/2 attempts to keep track of whether a given font is in use and to allow an application (including FontFolder and the OS/2 Font Pallete) to unload the font if it is not in use by another application. However, OS/2 appears to do a less than perfect job of tracking this, so it may or may not be possible to unload a font from memory. FontFolder takes the view that if the user said to unload the font, it should be shown in the Installed Fonts list as unloaded, so the Installed Fonts list is updated and the font removed from the list even if FontFolder was unable to unload the font from OS/2 memory. As noted above, the font will be gone the next time OS/2 boots. ═══ 10. FontFolder Menus. ═══ The menu items available in FontFolder are shown below. Click on the appropriate item for further information. o Master Library - Register Fonts - Delete Fonts - Save Master Library - Revert Master Library - Font Information o Options - View - Settings ═══ 10.1. Master Library Menu ═══ The choices on the Master Library menu are o Register Fonts o Delete Fonts o Save Master Library o Revert Master Library o Font Information ═══ 10.1.1. Register Fonts ═══ Select this menu item to register one or more fonts with the Master Library. When selected, a Register Fonts file dialog panel will appear which allows the user to select the drive and directory on which the fonts to be registered are located (the source location). Fonts are represented in the file dialog by their PFB file. Multiple font files may be selected. If the source location is on a removable drive an additional Copy Fonts to Hard Drive dialog panel will be displayed where the user can specify where to place the selected fonts on a hard drive (the target location). The user can also specify on this panel whether or not to copy any companion Windows font files that are found. If the operation is successful the fonts selected will appear in the Master Library list. This list must be saved to make these additions permanent. ═══ 10.1.2. Delete Fonts ═══ First mark one or more fonts in the Master Library list for deletion and then select this menu item from the Master Library pulldown on the menu bar to delete the marked fonts from the Master Library. FontFolder will prompt the user to confirm the deletion or cancel the operation. Upon confirmation the fonts will be deleted from the Master Library list. This list must be saved to make these deletions permanent. If no font has been marked before Delete Fonts is selected an error message is displayed and the operation is cancelled. No font files are deleted from the hard drive when a font is deleted from the Master Library list. Use the standard OS/2 file management facilities to delete the font files if desired. ═══ 10.1.3. Save Master Library ═══ Select this menu item from the Master Library pulldown to save a copy of the current Master Library list to disk in the file MASTLIB.FF1. If MASTLIB.FF1 already exists it will be converted to MASTLIB.BAK before the new copy is written. ═══ 10.1.4. Revert Master Library ═══ Select this menu item from the Master Library pulldown to make the backup copy of the Master Library file, MASTLIB.BAK, the current copy. Note: The existing current copy, MASTLIB.FF1, will in turn be made the backup copy, so two Revert operations cancel the operation. The current Master Library list held in memory and seen on the screen is reset to show the contents of the new current copy of the Master Library. ═══ 10.1.5. Font Information ═══ Mark a font in the Master Library list and select this menu item from the Master Library pulldown to see a popup window showing information about the selected font. This information includes the font name, the fully qualified path to the font file and a font text sample for the marked font. The point size of the font used in the text sample can be changed, and the user can revise the sample text. If the sample text is revised, the revised text will be saved and redisplayed in the future. Marking multiple items will not cause an error, but FontFolder will only show the font information for the first marked item. The user can also quickly select this item from the Main Window by clicking on the Font Information Button in the upper left corner of the window. The Font Information Button is shown below. ═══ 10.2. Options Menu ═══ The choices on the Options menu are shown below: o View o Settings ═══ 10.2.1. View ═══ The View menu option allows the user to change how the font lists are displayed in the main FontFolder window. The default display lists the fonts by their font names (e.g. Courier Bold). The user can also choose to have the lists display the fonts by their file names (COURB.OFM) or by their fully qualified path names (C:\PSFONTS\COURB.OFM). In each view the font lists are sorted alphabetically by the currently displayed names. Note: One way in which an alternate view is useful is that the path names view groups all fonts residing in the same directory together in the list so a user who wants to move a font directory for space or other reasons and needs to discover which font files from that directory are currently loaded in OS/2 can easily find them. All FontFolder functions are fully operational from whatever view is currently displayed. To select a new view, choose the View menu item from the Options pulldown on the menu bar, then choose the appropriate view from the submenu. ═══ 10.2.2. Settings ═══ Choose the Settings menu item from the Options pulldown to bring up the FontFolder Settings Dialog. From this dialog the user can o Edit the Removable Drives list o Change the path to the FONTFOLD.INI file o Change the path to the Master Library file, MASTLIB.FF1 o Set the default on whether or not to Copy Windows Font Files when registering files residing on removable media with the Master Library See the FontFolder Settings Dialog help for more details. ═══ 10.3. Help Menu Help ═══ Help is available for the following Help menu items: o Keys Help o Product information ═══ 10.3.1. Keys Help ═══ The following are the FontFolder shortcut keys. When the names of two keys are shown joined by a plus (+) sign, press both keys simultaneously. Main Window Shortcut Keys Key Purpose Ctrl+M Tab to Master Library list in Main Window Ctrl+O Tab to OS/2 Installed Fonts list in Main Window Ctrl+I Install font in OS/2 Ctrl+U Remove(Uninstall) font from OS/2 Menu Item Shortcut Keys Key Purpose Ctrl+R Register font with Master Library Ctrl+D Delete font from Master Library F2 Save Master Library Shift+F2 Revert Master Library Ctrl+Q Master Library font information Ctrl+N View fonts by fontname Ctrl+F View fonts by filename Ctrl+P View fonts by pathname Ctrl+S View/Change Settings ═══ 10.3.2. Product Information ═══ Selecting this menu item displays product related information such as the version number, author and date of production of FontFolder. ═══ 11. FontFolder Dialogs ═══ Help is available for the following FontFolder dialogs: o Setup Dialog o Settings Dialog o Copy Fonts to Hard Drive Dialog o Load Installed Fonts List Dialog ═══ 11.1. Setup Dialog ═══ The FontFolder Setup Dialog is displayed when first starting FontFolder and in any case when FontFolder cannot find the FONTFOLD.INI file on startup. This dialog presents the user with key choices that must be made before FontFolder can run. They are o Removable Drive Letters When the user trys to register a font with the FontFolder Master Library, FontFolder needs to check whether the source location for the font files is on a removable medium such as a diskette or a CDROM. If the font files are on a removable medium, FontFolder must copy them to a location on a nonremovable drive (a hard drive) as part of the registration process. OS/2 requires that fonts reside on a hard drive when installed. FontFolder uses the Removable Drive Letters entry to identify the removable drives. The user should enter the drive letters of all the removable drives on the system in the Removable Drive Letters entry field. The form of the entry is the drive letters with no spacing or other punctuation. Example: If the system has two diskette drives, A and B, and a CDROM drive identified as F, then the Removable Drive Letters entry should be ABF Failure to properly identify the removable drives can lead to unpredictable results. o Path to FontFolder INI file The first time FontFolder is closed it creates a file called FONTFOLD.INI and writes a set of information about its state to the file. Examples of the type of information are the size and location of the FontFolder window on the screen, the Removable Drive Letters setting, and the location of the Master Library file. The default is to create this file in the same directory as FONTFOLD.EXE. However the user may want to locate the file in a different directory. For example, if FontFolder resides on a network server and is shared by several users, each user needs an individual copy of FONTFOLD.INI. In this case the user should change the path to the FontFolder INI file to point to a location on the local workstation. If the path to the FontFolder INI file is changed, an entry is made in OS2.INI specifying where this file is located. o Master Library Path The Master Library data file, MASTLIB.FF1, contains the font registration information for the Master Library. The default is for this file to reside in the same directory as the FONTFOLD.EXE file, but the user can change the path to point to another location. The Master Library Path information is stored in FONTFOLD.INI. One consideration in deciding where to locate the Master Library data file is the size of this file. The size will vary depending on the number of fonts registered with the Master Library. For the largest library that FontFolder can currently support the size of MASTLIB.FF1 would be approximately 360KB. Since one backup copy, MASTLIB.BAK, is also maintained, the maximum total space requirement for the Master Library files is approximately 720KB. However, this assumes the font file information stored includes maximum length path names. In actual practice the Master Library files will probably only be 20-30% of this size. ═══ 11.2. Settings Dialog ═══ The Settings Dialog is displayed when the user chooses Settings from the Options pulldown on the menu bar. From this Dialog the user can set the following FontFolder settings: o Removable Drive Letters When the user trys to register a font with the FontFolder Master Library, FontFolder needs to check whether the source location for the font files is on a removable medium such as a diskette or a CDROM. If the font files are on a removable medium, FontFolder must copy them to a location on a nonremovable drive (a hard drive) as part of the registration process. OS/2 requires that fonts reside on a hard drive when installed. FontFolder uses the Removable Drive Letters entry to identify the removable drives. The user should enter the drive letters of all the removable drives on the system in the Removable Drive Letters entry field. The form of the entry is the drive letters with no spacing or other punctuation. Example: If the system has two diskette drives, A and B, and a CDROM drive identified as F, then the Removable Drive Letters entry would be ABF Failure to properly identify the removable drives can lead to unpredictable results. o Path to FontFolder INI file The first time FontFolder is closed it creates a file called FONTFOLD.INI and writes a set of information about its state to the file. Examples of the type of information are the size and location of the FontFolder window on the screen, the Removable Drive Letters setting, and the location of the Master Library file. The default is to create this file in the same directory as FONTFOLD.EXE. However the user may want to locate the file in a different directory. For example, if FontFolder resides on a network server and is shared by several users, each user needs an individual copy of FONTFOLD.INI. In this case the user should change the path to the FontFolder INI file to point to a location on the local workstation. If the path to the FontFolder INI file is changed, an entry is made in OS2.INI specifying where this file is located. o Master Library Path The Master Library data file, MASTLIB.FF1, contains the font registration information for the Master Library. The default is for this file to reside in the same directory as the FONTFOLD.EXE file, but the user can change the path to point to another location. The Master Library Path information is stored in FONTFOLD.INI. One consideration in deciding where to locate the Master Library data file is the size of this file. The size will vary depending on the number of fonts registered with the Master Library. For the largest library that FontFolder can currently support the size of MASTLIB.FF1 would be approximately 360KB. Since one backup copy, MASTLIB.BAK, is also maintained, the maximum total space requirement for the Master Library files is approximately 720KB. However, this assumes the font file information stored includes maximum length path names. In actual practice the Master Library files will probably only be 20-30% of this size. o Copy Windows Font Files checkbox When the font that a user registers with the Master Library resides on a removable drive such as a diskette or CDROM drive, FontFolder must copy the font files to a hard drive location in order for OS/2 to use them. If the Copy Windows Font Files checkbox is checked then FontFolder will also copy the appropriate Windows font files to the hard drive. ═══ 11.3. Copy Fonts to Hard Drive Dialog ═══ When the font that a user registers with the Master Library resides on a removable drive such as a diskette or CDROM drive, FontFolder must copy the font files to a hard drive location in order for OS/2 to use them. The Copy To Hard Drive dialog will be displayed, and the user must enter the path to the directory on the hard drive where the fonts should be copied. A checkbox gives the user the option of making the path entered the default for future Copy Fonts to Hard Drive dialogs. The user also may change the Copy Windows Font Files setting as shown in the Copy Windows Font Files checkbox. If the Copy Windows Font Files checkbox is checked then FontFolder will also copy the appropriate Windows font files to the hard drive. This setting may also be changed from the Settings menu. ═══ 11.4. Load Installed Fonts List Dialog ═══ This dialog box appears during FontFolder startup when FontFolder encounters a font already installed in OS/2 that is either unreadable by OS/2 or for which the OS/2 font information is corrupt. It is possible to add such fonts to the list of OS/2 Installed Fonts using the OS/2 Font Pallete. However, OS/2 cannot use such fonts, and they do not show up in the Font Pallete. FontFolder rejects these fonts. The Load Installed Fonts List dialog shows the name of the unusable font file, and gives the user the option of either removing it from the list of Installed Fonts or leaving it alone. In either case, FontFolder will not show this font on its list of Installed Fonts. Normally the user should choose to Remove the font. The only case where one might choose otherwise is if the user wants to temporarily leave it alone while the user investigates to understand what the problem might be with the font file. If the user chooses the Leave Alone option, this dialog box will reappear every time FontFolder is started, until the user chooses Remove. ═══ 12. Error Recovery ═══ See the following for help with specific errors: o Listbox Error ═══ 12.1. Listbox Error ═══ Error Message: OS/2 can not insert any more items in the listbox name listbox. Your data should be safe. Refer to the Help section on Error Recovery for instructions on how to recover from this error. Explanation: This error occurs when OS/2 has reached its limit of 64K bytes of listbox text for all listboxes in the system. In FontFolder this usually only occurs when in full pathname view mode and the font directory paths are very long. If you have large numbers of fonts stored in directories with long path names, try the following: 1. If you are not already in Pathname view mode, switch to this mode, ignoring the error message. 2. Select all the entries in the Master Library listbox that are located in the directory with the long path name. 3. Select Delete from the Master Library menu. 4. Select Pathname view mode again from the Options menu to refresh the listboxes and repeat steps 2 and 3. Do this as many times as is required to purge all the items for the long path name directory. 5. Save the Master Library. You should now be able to switch in and out of the Pathname view mode without encountering the Listbox error. If not, you may have to repeat the above steps for another directory. 6. If any of the fonts you have just removed are installed in OS/2, uninstall them. 7. Close FontFolder and reboot the system. The reboot may not be necessary, but you should do it anyway as a safety precaution. 8. Reorganize your font directories so that they have shorter path names, and then re-register the fonts with FontFolder. If after doing the above, you still get the Listbox error message, you have reached the limit of the total number of fonts you can register in FontFolder. Remove fonts using the above procedure until the error message no longer occurs. ═══ ═══ FontFolder uses the term register in the sense that information about the font and where to find the font files is added to the library. This term is used in preference to add to try to make the point that no files are added to the system as part of the registration process. The exception to this is when the files reside on a removable drive, in which case FontFolder both registers them and adds them to the system.